Method and system for hosting entity-specific photo-sharing websites for entity-specific digital cameras

ABSTRACT

A system and method hosts entity-specific photo-sharing websites for entity-specific image capture devices. The system and method provides software for the entity-specific image capture devices that causes the image capture devices to transmit entity ID information when the image capture devices transmit images over the Internet. The system and method further provide an online photosharing service capable of hosting the entity-specific photo-sharing websites for each of the entities, such that when the image capture devices connect to photo-sharing service, the photo-sharing service uses the entity ID received from the image capture devices to automatically associate the image with the photo-sharing websites of the identified entity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to pending U.S. patent application Ser. No. 14/144,285, filed Dec. 30, 2013, which is a continuation of and claims priority to U.S. patent application Ser. No. 13/523,627, filed Jun. 14, 2012, now issued as U.S. Pat. No. 8,645,325, which is a continuation of and claims priority to U.S. patent application Ser. No. 09/625,398 filed Jul. 26, 2000, now issued as U.S. Pat. No. 8,224,776, all of which are incorporated herein in their entirety. This application is also related to U.S. Ser. No. 09/626,418, filed Jul. 26, 2000, now issued as U.S. Pat. No. 7,117,519, and U.S. Ser. No. 09/625,824, filed Jul. 26, 2000, now issued as U.S. Pat. No. 6,636,259.

FIELD OF THE INVENTION

The present invention relates to a method and system for hosting web-based photo-sharing websites, and more particularly to a method and system for customizing digital cameras to upload images to an entity-specific photo-sharing websites.

BACKGROUND OF THE INVENTION

As popularity of digital cameras grows, the desire of digital camera user to share their images with others will also continue to grow. New digital camera owners typically try to share their images based on the paradigm of film cameras, in which images are printed on paper and then placed into a photo album. The most straightforward approach to do this with a digital camera is to connect the digital camera directly to a printer to create the prints, and then manually insert the images into a photo album. Users often find this process somewhat complicated and restrictive because standard printers can only print images in limited sizes and requires particular types of paper. And even after the photo album has been assembled, the printed images are not easily shared with many people.

The best approaches to photo-sharing take advantage of the Internet. One such approach is for users to store the digital images on a PC and then send the images to others using email. Several Internet companies now offer an even more convenient approach by providing photo-sharing websites that allow users to store their images for free and to arrange the images into web-based photo albums. Once posted on a photo-sharing website, others may view the images over the Internet.

While convenient for storing digital images, getting the images to the photo-sharing websites can be challenging for users. Most commonly, users must upload their images from the digital camera to a PC using a cable or IrDA, or by inserting the camera's flash card into the PC. From the PC, the user logs onto the Internet and uploads the images to a photo-sharing website. After uploading the images, the user works on the website to arrange the images into web albums and to add any textual information.

Although today's approach for storing images from a digital camera onto a web photo-sharing website and for creating web photo albums works reasonably well, two problems remain that hinder the mainstream adoption of web-based photo-sharing. One problem is that this approach requires the use of a PC, notebook computer, or PDA. While many digital camera users today have PC's, most of those users are early adopters of technology. There are many other consumers who would purchase a digital camera, but are reluctant to do so because they do not yet own a PC or are intimidated by them.

In an effort to address this problem, the assignee of the present application developed an approach to uploading images to the web that doesn't require the use of a PC. In this approach, an email software application is loaded into a digital camera capable of running software that allows the user to e-mail the images directly from the camera. The user simply connects his or her digital camera to a cellphone or modem, runs the e-mail application, and selects the desired images and the email recipients. The selected images are then sent to the recipients as e-mail attachments.

Although emailing photos directly from the camera allows users who do not own a PC to share images over the Internet, these users must still establish accounts with both an Internet service provider (ISP) and the photo-sharing website before being able to post their images. These accounts must also be set-up by PC users as well. For techno savvy users who use a PC to upload the images to the photo-sharing website, establishing the accounts may not be a bother, but even these users may not always have their PCs handy, such as when on vacation, for instance. And for non-PC users, establishing the accounts by entering account information on the digital camera itself may prove to be a cumbersome, if not a daunting, task.

Accordingly, what is needed is an improved method for uploading images from a digital camera to a photo-sharing website on the Internet. In order for online photo-sharing to become more mainstream, an approach that doesn't require a PC or PC expertise and that reduces complexity for the user is required. The present invention addresses such a need.

SUMMARY OF THE INVENTION

The present invention provides a method and system for hosting entity-specific photo-sharing websites for entity-specific image capture devices. The system and method provide software for the entity-specific image capture devices that causes the image capture devices to transmit entity ID information when the image capture devices transmit images over the Internet. The system and method further provide an online photo-sharing service capable of hosting the entity-specific photo-sharing websites for each of the entities, such that when the image capture devices connect to photo-sharing service, the photo-sharing service uses the entity ID received from the image capture devices to automatically associate the images with the photo-sharing website of the identified entity.

According to the system and method disclosed herein, the photo sharing service of the present invention provides digital cameras users with an automatic solution for uploading captured images from a digital camera to an online photo-sharing website, without a PC. The photo sharing service also provides companies, such as camera manufactures, with a complete end-to-end solution for their cameras. The solution includes customized software for their cameras for sending images over the internet, and a branded photo-sharing website for storing images from those cameras that appears to be hosted by the company. Thus, the photo sharing service provides both business-to-consumer and a business-to-business services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an online photo-sharing system in accordance with a preferred embodiment of the present invention.

FIG. 2 is a flow chart illustrating a business method for hosting entity-specific photo-sharing websites for entity-specific image capture devices in accordance with a preferred embodiment of the present invention.

FIG. 3 is a diagram showing a preferred embodiment of the connectivity and application software of the camera.

FIGS. 4A and 4B illustrate a flow chart of a process for automatically configuring a web-enabled digital camera to access the Internet in a preferred embodiment of the present invention.

FIG. 5 is a block diagram illustrating an example action list 48 displayed on the LCD screen of the camera.

DESCRIPTION OF THE INVENTION

The present invention relates to an automatic system for uploading images from a digital camera to entity-specific photo-sharing websites and for automatically establishing accounts. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.

FIG. 1 is a block diagram illustrating an online photo-sharing system 10 in accordance with a preferred embodiment of the present invention. The system includes a plurality of camera controlling entities 12 that produce, own, or otherwise control a set of digital cameras 14, and an online photo-sharing service 16. The online photo-sharing service 16 includes a gateway server 18 and an entity/account database 20. The various camera controlling entities 12 contract with the photo-sharing service 16 to transparently host customized photo-sharing websites 22 for each entity, which are referred to herein as entity-specific photo-sharing websites 22. The entity-specific photo-sharing websites 22 are each accessible to the user through the entity's existing Internet site (not shown), and thus appear to users as though the entity-specific photo-sharing websites 22 are hosted by the corresponding entity. According to a preferred embodiment of the present invention, the cameras 14 for a particular entity are customized for that entity to create entity-specific cameras 14, such that when the cameras 14 connect to the Internet, the cameras 14 automatically upload their images to the photo-sharing website of the corresponding entity. In a further aspect of the present invention, the photo-sharing service 16 automatically stores the images in a web album, which is viewable over the Internet by a user's web browser 24.

As used herein, a camera controlling entity 12 is any entity that makes, owns, sells, or controls digital cameras 14, and therefore includes, camera manufactures, companies, retailers, and end-users. One or more combination of these entities 12 may either contract with the photo-sharing service 16 to provide entity-specific websites 22 for their cameras 14, or have entity information transmitted to the photo-sharing service 16 from the cameras 14. Therefore, a camera controlling entity 12 may include a single entity 12 or a hierarchal relationship of entities 12.

An example of a single entity 12 includes an insurance company that contracts with the photo-sharing service 16 to have all digital cameras 14 used by their agents to transmit their images to a customized insurance photo-sharing website. Examples of a hierarchal relationships of entities 12 includes a camera manufacturer, such as Nikon, that contracts with the photo-sharing service 16 to have all Nikon digital cameras 14 transmit their images to the customized Nikon photo-sharing website. Since the images of different users must be distinguished, each user of a Nikon camera 14 would also constitute an entity within the Nikon website so that the images from different users can be distinguished. Other examples of hierarchal entity relationships include a retailer and its consumers, a real estate agency and its agents, community groups and its members, and government agencies and its employees, for instance.

In a preferred embodiment, the cameras 14 are customized for their respective entities 12 by providing the cameras 14 with software for transmitting entity ID information 28 identifying its controlling entity 12 to the photo-sharing service 16. The photo-sharing service 16 in conjunction with the gateway server 18 and the entity/account database 20 hosts the entity-specific photo-sharing websites 22. Each entity-specific website 22 is identified in the database 20 by an entity account number 30 and includes the web pages and URLs 32 comprising the website, the images and web albums 34 stored on the website, and the user account numbers 36 of authorized users. The database 20 also includes user accounts 40, each of which comprises a user account number 42, user preferences 44, the user's images 46, and action lists 48, explained further below.

The gateway server 18, which communicates with the cameras 14 during image uploading, receives one or more entity IDs 28 from each camera 14 and matches the entity ID 28 with an entity account 30 in the database 20. The images are then automatically associated with the photo-sharing website 22 of the identified entity 12 and/or the identified user.

After the images are uploaded, a user of the camera 14 may visit the online photo-sharing website 22 over the Internet to view the images via a web browser 24. Since the photo-sharing websites 22 are transparently hosted by the photo-sharing service 16, each photo-sharing website 22 appears as though it is hosted by the entity itself, rather than the third party service.

In one embodiment, the cameras 14 may connect to the Internet via a service provider 26, which may include a wireless carrier and/or an Internet service provider (ISP) that is capable of servicing many devices simultaneously. In a preferred embodiment, each of the cameras 14 is provided with wireless connectivity for connecting to the Internet, and are therefore so called “web-enabled” devices, although a wired connection method may also be used.

The cameras 14 may be provided with wireless connectivity using anyone of a variety of methods. For example, a cellphone may be used to provide the digital camera 14 with wireless capability, where the camera 14 is connected to the cellphone via a cable or some short-range wireless communication, such as Bluetooth. Alternatively, the camera 14 could be provided with built-in cellphone-like wireless communication. In an alternative embodiment, the digital camera 14 is not wireless, but instead uses a modem for Internet connectivity. The modem could be external or internal. If external, the camera 14 could be coupled to modem via any of several communications means (e.g., USB, IEEE1394, infrared link, etc.). An internal modem could be implemented directly within the electronics of camera 14 (e.g., via a modem ASIC), or alternatively, as a software only modem executing on a processor within camera. As such, it should be appreciated that, at the hardware connectivity level, the Internet connection can take several forms. Hence, it should be appreciated that the present invention is not limited to any particular method of accessing the Internet.

In a preferred embodiment, the entity-specific websites 22 are customized to seamlessly integrate into the entity's existing website by following the look and feel of the entity's existing website. The entity-specific websites 22 are hosted on the photo-sharing service 16, but a link to the entity-specific websites 22 may be provided on the homepage of the corresponding entity's existing website. Thus, in order to view a web album on an entity-specific website 22, the user must visit the entity's existing website and click the link to the entity-specific website 22, where the user's browser 24 will be transparently directed to the photo-sharing service 16 and be provided with the web pages 32 of the entity-specific website 22.

As an example of the operation of the photo sharing system 10, consider the following scenario. Assume that Minolta and Nikon are entities 12 that have contracted with the photo-sharing service 16, and that the photo-sharing service 16 hosts a photo-sharing website 22 for Minolta and a photo-sharing website 22 Nikon. The Minolta cameras 14 would be provided the entity ID 28 for Minolta and the Nikon cameras 14 would be provided the entity ID 28 for Nikon. When the Minolta and the Nikon cameras 14 send sets of images to the photo-sharing service 16, the gateway server 18 would distinguish the cameras 14 by the entity IDs 28 and would direct the set of images received from Minolta cameras 14 to Minolta's photo-sharing website, and would direct the images from Nikon cameras 14 to Nikon's photo-sharing website. To view the images, the owners of the cameras 14 would use a browser 24 on their PC or PDA to visit the URL of the Minolta or Nikon photo-sharing websites 22. In one preferred embodiment, the photo-sharing service 16 sends the URL of the entity-specific website 22 directly to the camera 14 for display to inform the user of the address.

According to the present invention, the photo-sharing service 16 provides business-to-business and business-to-consumer business models. The service is business-to-business because the service provides companies, such as camera manufactures, with a complete end-to-end solution for their cameras 14. The solution includes customized software for their cameras 14 for sending images over the internet, and an internet website for storing images from those cameras 14 on a branded website that appears to be hosted by the company. The service is business-to-consumer because it allows users of digital cameras 14 with an automatic solution for uploading captured images from a digital camera 14 to an online photo-sharing website, without a PC.

According to one preferred embodiment of the present invention, the photo-sharing service 16 provides a method of doing business whereby the photo-sharing service 16 shares revenue based on the hierarchal relationship of the entities 12. For example, if the photo sharing service 16 charges a fee for receiving and/or storing the images received from the entity-specific cameras 14, then the photo sharing service 16 may share a portion of the fee with the manufacturer and/or third party supplier of the camera 14 that uploaded the images, for instance. Revenue may also be shared with the wireless service provider providing the connection with the photo sharing service 16.

FIG. 2 is a flow chart illustrating a business method for hosting entity-specific photo-sharing websites for entity-specific image capture devices, such a digital cameras, in accordance with a preferred embodiment of the present invention. First, the cameras 14 are provided with connectivity and application software for communicating over the Internet in step 50. In a preferred embodiment, this step is performed during camera 14 manufacturing to provide off-the-shelf web enabled cameras 14. The cameras 14 are also customized for specific entities 12 to create entity-specific cameras 14 by providing each of the cameras 14 with at least one entity ID 28 identifying the corresponding controlling entity in step 52.

Referring now to FIG. 3, a diagram showing the preferred embodiment of the connectivity and application software of the camera 14 and the entity ID 28 information is shown. Preferably, the camera 14 includes a microprocessor-based architecture that runs an operating system 70 for controlling camera hardware 72 and overall functionality of the camera 14 (e.g., taking pictures, storing pictures, and the like). An example of such an operating system 70 is the Digita™ Operating Environment developed by the assignee of the present application. The camera 14 also includes communication manager 74 software, and a TCP-IP protocol stack 76, that enables communication via the internet, as is well-known in the art. The entity ID information 28 and captured images may be stored in one or more types of memories 82.

For hierarchal entity relationships, the cameras 14 are provided with hierarchal entity IDs 28; one entity ID 28 identifying the entity, and a second entity ID 28 identifying the end-user. Whether there are one or more entity IDs 28, the entity ID 28′ of the camera manufacturer may always be provided. Camera 14 customization may occur either during manufacture or anytime thereafter. In a preferred embodiment, the manufacturer entity ID 28′ is provided at the time of manufacturing and is stored in an EEPROM 82 b, while the entity IDs 28 for other entities 12, such as companies and end-users, are loaded into the camera 14 subsequent to manufacturing and are stored in flash memory 82 a or the EEPROM 82 b.

Customization that occurs subsequent to manufacture may be implemented using several methods. The first method is to manufacture the cameras 14 with an application programming interface (not shown) for accepting a subsequently loaded software application that specifies the entity ID's 28. The application may come preloaded on a flash card, which is then inserted into the camera 14 by the user and stored in flash memory 82 a. The application may also be wirelessly beamed into the camera. When executed in the camera, the software application transmits the appropriate entity IDs 28 to the gateway server 18.

The second method is to load a small file in the camera 14 specifying the entity IDs 28 from a removable memory or from a PC, and storing the file in a system folder within the camera's flash memory 82 a. The camera 14 then accesses the file when an Internet connection is established. In a preferred embodiment, the communication manager 74 automatically extracts the manufacturing ID 28′ and the entity ID 28 and transmits them to the gateway server 18. In this embodiment, the entity ID 28 is also stored in the EEPROM 82 b and is factory set to zero (empty). Thus, unless the entity ID 28 is set, the manufacturing ID 28′ may default as the highest controlling entity.

If, for example, a third party developer X contracts to provide custom camera software for camera manufacturer Z, then a custom entity ID will be issued for developer X and developer X will place the custom entity ID into the EEPROM 82 b. Developer X is now a controlling entity 12, and may specify to the photo-sharing service 16 that a developer X entity-specific photo-sharing site 22 or developer X's own website be the destination for the uploaded images.

The protocol stack 76, under direction of the communications manager interfaces with the communications hardware 78 of camera. The protocol stack 76 includes software APIs and protocol libraries that interface with the communication manager 74, and communication hardware interface drivers that interfaces directly with the various communications hardware 72 the camera 14 must function with (e.g., a Bluetooth transceiver, etc.). The communication manager 74 communicates with operating system 70 and the IP protocol stack 76 to establish an Internet connection and to transmit the entity ID 28 information and images from the memories 82 a and 82 b to the photo-sharing service 16.

In an alternative embodiment, rather than loading entity ID's 28 into the camera, a combination of the camera's serial number and the make and model number of the camera may be used as the entity ID 28. Entity specific cameras 14 may then be distinguished by providing a mapping of the camera serial numbers and product IDs to specific entities 12 in the database 20. Although the camera 14 has been described in terms of a software-based customization solution, those with ordinary skill in the art will readily recognize that the camera 14 may also be provided with a hardware-based solution.

Referring again to FIG. 2, before or after camera customization, the entity-specific websites 22 are created for each entity contracting with the photo-sharing service 16 in step 54. Customization requires storage of entity information in the entity/account database 20 and creating and storing web page elements comprising the entity-specific photo-sharing website in the database 20. The entity-specific information stored in the database 20 may also include service levels, and enabled features for the entity-specific website 22. Features are components or services that may be provided on websites by the photo-sharing service 16, such as search functions, and online printing, for instance, but may be selectable by each entity for its own website. As an example, company X may provide customized cameras 14 for its employees, but may not wish to allow employees to print images from the company X photo website for security reasons. If so desired, company X may have the photo service disable this feature from their particular website.

In a preferred embodiment, the entity-specific websites 22 are not created from scratch, but are created by modifying a preexisting template. The template may include several different sections, such as A, B, C and D, for instance. Assuming for example that the template used to create a website for Nikon, and section A is used to specify the name of the entity then the name Nikon would be inserted into that section. Other entity-specific content would be used to fill out the remaining sections. The Web pages comprising the Nikon specific photo-sharing website would then be provided with URL's unique to that website. The entity's regular website would be modified to include a link to the entity's photo-sharing website 22. In addition, the entity-specific photo-sharing website would include a link back to the entity's website. Entities 12 may have entity photo-sharing web sites 22 created for them in one of two ways; automatically by logging into the photo-sharing service 16 and manually customizing the templates, or by having the entity photo-sharing website created for them.

Referring still to FIG. 2, when a camera 14 establishes an internet connection with the gateway server 18, the camera 14 transmits its entity IDs 28 and/or user entity ID 28 when uploading user selected images to the gateway server 18 in step 56. In response, the gateway server 18 matches the entity ID 28 with an entity account in the database 20 and matches the user entity ID 28 with a user account 40 in the database 20 in step 58. The images received are then stored in the user account 40 of the identified entity-specific website 22 in step 60.

Referring again to FIG. 1, each user account 40 in the database 20 may also include one or more action lists 48. According to the present invention, an action list 48 includes one or more items representing actions that the gateway server 18 should take with respect to uploaded images, such as where to store and/or send the images from a particular user or camera, for instance. As explained further below, the action list 48 stored on the database 20 under a user's account 40 are automatically downloaded to the user's camera 14 during a connection with the gateway server 18 and stored on the camera 14. When the user initiates an image upload, the action list 48 is displayed to the user so the user may easily select what actions the gateway server 18 should take with respect to the images by selecting the displayed action list items.

Examples of action list items include specifying that the uploaded images should be stored on the entity-specific photo website, sending the images to a list of email addresses, or even performing some type of analysis or calculation on the image data, for instance.

In a further aspect of the present invention, an action list item is not limited to instructing the gateway server 18 to perform actions only within the photo-sharing service 16. Rather, an item in the action list 48 may also instruct the gateway server 18 to perform actions outside of the photo-sharing service 16, such as storing the images in an external database 49 of the entity 12. For instance, in the example where the entity 12 is a company, some users of the company's cameras 14 could have action lists 48 instructing the gateway server 18 to store uploaded images to the company's database, rather than to the company's photo-sharing site 22. Based on the action lists 48 and customization, the gateway server 18 may be programmed to automatically perform predefined tasks, such as creating new web albums, or a new page within an existing album, parse the images to extract sound files or other metadata, print images and mail them to designated addresses, and so on.

In a preferred embodiment, the action lists 48 may be created via several methods. In one method, the action list is created by the photo-sharing service 16 the first time the user's camera establishes a connection. That is, a default action list 48 is automatically created based on the entity ID when a user account 40 is first created. In a hierarchal entity relationship where the entity 12 is a company, a default action list 48 may be created to implement a workflow specified by the entity 12. In a hierarchal relationship where the entity 12 is camera manufacturer, for instance, a default action list 48 may be created instructing the gateway sever 18 to store the user's images in a simulated “shoebox” on the entity-specific photo-sharing site 20. The user may then go online and create albums from the images in the shoebox as desired.

Another method is for the user to create the action list 48 online on the entity-specific photo-sharing site 20. The action list 48 may be created manually on the website 20 by the user navigating to the site 20 using a web browser 24, accessing her account, and manually creating the action list 48 or editing the action list 48 on the entity-specific site 22. The action list 48 may also be created automatically on the website 20 in response to user actions performed on the website, such as printing images, or creating a web album. Alternatively, after performing an action, the user may be prompted whether they would like this action added to his or her action list 48. If so, the user clicks a check-box and the item is added the action list 48. In a preferred embodiment, any action list 48 created and edited on the photo-sharing site 20 are downloaded to the camera every time the camera 14 connects to the photo-sharing service 16 and made available for user selection on the camera 14 during the next upload.

Yet another method for creating an action list 48 is to allow the user to create the action list on the camera 14. The user may manually create an action list 48 by “typing” in predefined items on the camera. The user may also type in an email address as an action list item whereby when that item is selected, the uploaded images are stored as a web album on the entity-specific photo-sharing website 22 and the server 18 sends a notification to the specified recipient containing the URL to the web album page.

A method and system for hosting web-based photo-sharing websites and for customizing digital cameras to upload images to the entity-specific photo-sharing websites has been disclosed. According to the present invention, users of the customized cameras 14 can upload images to the Internet for storage and web photo album creation without the use of a PC.

In one embodiment described above, the present invention assumes that an ISP account has been established with the digital camera's service provider, and that users of cameras 14 belonging to a certain entity 12 may use the cameras 14 to upload images to the website of the entity 12. However, two problems with account setup remain. One problem is that just as with a PC and PDA, the user must first establish an ISP account before the camera 14 can establish Internet communication. The second account problem is that most websites, including the photo sharing sites 22, may require each user to establish a unique account before using the site to distinguish one user from another. Before being able to connect the web-enabled camera 14 to the Internet, the user must establish these two accounts by either entering account setup information on a PC or entering account setup information on the camera 14. Neither alternative is a convenient alternative for people who do not have the time nor inclination to do so.

In a further aspect of the present invention, the cameras and the photo sharing site are provided with software for automatically creating Internet and photo-sharing website accounts for each camera 14 upon first use, without requiring the user to first enter account information on a PC or on the camera 14.

Referring now to FIGS. 4A and 4B, a flow chart illustrating a process for automatically configuring a web-enabled digital camera to access the Internet in a preferred embodiment of the present invention. Although the process will be described in terms of automatically establishing Internet accounts for a digital camera without requiring the user to enter information, those with ordinary skill in the art will readily recognize that the present invention may be used to automatically establish Internet accounts for any type of portable electronic device.

The process assumes that a user has just acquired a digital camera 14 customized as described above, and has just taken the camera 14 out of its box in step 100. After taking pictures with the camera in step 102, the user may review the images in the camera's LCD screen and optionally select a set of images to upload to the photo sharing service 16 in step 104. The user then presses a “send” button on the camera in step 106 to upload the images.

In response, the camera displays a confirmation dialog screen on the camera and prompts the user to record an audio annotation for the images or to continue in step 108. The user may then choose to record audio for the images in step 110. After choosing to continue, or after recording audio, the camera displays a “connecting” dialog screen in step 112 to indicate to the user that the camera is establishing an Internet connection. At the same time, the camera checks for available connection options in step 114, and if more than one is found, the camera prompts the user to select one of the connection options. For example, the camera may be within range of a Bluetooth-equipped printer and a cellphone, so the user will be prompted to choose which device the camera should establish communication with.

The camera then checks for the presence of account information on the camera in step 116, and if there are none, the camera assumes that this is a first-time connection. According to the present invention, in order to allow the camera to make a first-time Internet connection, the camera is provided with default Internet service provider (ISP) information during manufacturing, including an ISP access number, and user ID and password (if required). The camera establishes connection with the default ISP in step 118 by dialing the preloaded access number, and by sending the preloaded user ID and password to the ISP. This special account may be configured so that the camera can only connect to the gateway server 18 (no other IP addresses may be allowed).

After connecting with the ISP, the camera connects to the gateway server 18 and sends unique camera information and/or user information in step 120. In a preferred embodiment of the present invention, a combination of the camera's serial number and the make and model number of the camera may be sent as the unique camera information. In another preferred embodiment, the user's e-mail address may be sent as the unique camera or user information.

Continuing with FIG. 4B, the gateway server 18 uses the unique camera information to set up a user account 40 in step 122. After creating the user account 40, the gateway server 18 returns an information packet to the camera containing new ISP information (if needed), an account ID, and an account password in step 124. The information packet may also contain a default action list specifying what actions should be taken with respect to the images, an advertisement for display on the camera, and the URL of the entity-specific website 22.

It should be noted that if the camera is used in conjunction with an IP direct phone or is provided with a phone number for connected to a dedicated server where the user is not billed separately for the ISP connection, then the steps of providing the camera with default ISP info and returning new ISP info, may be omitted.

The camera receives the information packet in step 126, and writes a configuration file to memory 82 a containing the ID, password, and default action list in step 128. The camera then displays the action list on the camera's LCD screen for selection by the user in step 130. The camera may optionally display the user's account information as well.

In an alternative preferred embodiment where security is a concern, the camera 14 to first logs off the special ISP and the gateway accounts, and then reconnects using new ISP and gateway accounts in order to retrieve the action lists 48.

FIG. 5 is a block diagram illustrating an example action list 48 displayed on the LCD screen of the camera 14. The action list 48 is shown displaying three major options; printing the uploaded images, saving the uploaded images in the user's shoebox, and sending the images to Mom. Under the printing option, the user may select from various size prints. Rather than nested menu categories as shown under the printing option, the action list 48 may be displayed with each action listed as a separate item (e.g., “Send 4×8 prints to Mom”, “Send 5×7 prints to me”).

Referring again to FIG. 4B, after the user selects one or more actions from the action list 48, the camera begins to upload the images along with the selected actions in step 132 and displays a progress bar on the screen in step 134. In one preferred embodiment, the camera may also display the advertisement sent in the information packet from the gateway server 18. The advertisement may advertise the controlling entity 12, the entity's photo-sharing site 22, or the photo sharing service 16. After all the images are uploaded and associated with the user's account 40, the camera breaks the connection with the gateway server in step 136. At this point, the camera 14 may also display the URL of the entity-specific website 22 to the user.

The next time the user uploads images, the camera will use any new ISP information received to connect to the Internet and will use the account ID and password written to memory 82 a when connecting to the gateway server 18. Thus, by using unique camera information, such as the serial number, to establish a web site account upon first use, the present invention eliminates the need for the user to type in information to establish a web site accounts.

To further explain the present invention from a user interaction point of view, consider the following scenario where a user named Jack has just purchased a digital camera 14 from a store and unpacks the camera from the box. There is a “Quick Start Guide” which guides him in getting started. Jack pops in the batteries, sets the date and time, and takes some pictures of his dog and his new baby. Jack can see the pictures have come out well on the small LCD, and now wants to try sharing them with his parents.

The Quick Start Guide says to select the photos to be sent using the “Select” button, and then press the “Send” button. So, Jack navigates to each of the baby pictures, selects them, and then presses the “Send” button. Instantly, a dialog comes up on the LCD screen: “No Receiving Device Found! Please turn on your phone or other connecting device.” Oops! Jack pulls out his cell phone, and turns it on. He presses the “Continue” button. Jack does not see this happen, but the camera now “discovers” the cell phone, and immediately presents another dialog: “4 Images Selected. Press Record to add a Sound Note, or Continue to send”. Although Jack finds the proposition of recording sound intriguing, he decides to skip it and presses the “Continue” button. Immediately, the dialog is replaced with a “Connecting . . . ” dialog.

Shortly, another dialog appears: “Your camera serial number is 38147. Please write this down. You will need it to access your web photo albums”. Jack writes the number down on the spot provided in the Quick Start Guide, and presses OK.

Another “Connecting . . . ” dialog appears, and is then quickly replaced by another dialog, which says “A free, temporary account has been set up for you at www.photo-sharing service.com/new_accounts. You will need your camera serial number to access your photos and complete the setup of your account. Please complete the account setup within 30 days”. Jack writes down the URL in the space provided in the Quick Start Guide, and presses the OK button. Jack doesn't know it, but during this dialog, the camera has begun transmitting his images and is already partially complete.

A new dialog comes up, with a progress bar. Jack is surprised to see that the transmission is already almost ⅓ done. Below the progress bar, the dialog says “Press “Continue” to use camera during photo transmission, or wait for progress bar to complete”. Jack is interested in watching how fast his images are transmitted, and decides to watch the progress bar complete. A “Transmission Successful” dialog appears. Jack presses the OK button. The camera returns to the review mode.

Jack is pretty excited—he just sent four baby pictures to the Internet. Jack then decides to see what happened to his images so he turns on his PC. After connecting to the Internet, Jack types in the URL from the Quick Start Guide. A Photo-sharing service web page appears, welcoming Jack to the photo-sharing service. After looking briefly at the welcome page, Jack types in his serial number from the Quick Start Guide, and selects his camera's model number from a pop-up menu. Jack clicks on a “Submit” button on the web page.

Jack now sees a page which shows thumbnails of the baby pictures he just sent, the page is entitled “My Shoebox”. The page explains to Jack that he is looking at his on-line digital photo shoebox. Since the server 18 knows this is Jack's first visit, special help messages may appear. Various options are provided via buttons and text links. One that catches Jack's eye is CREATE WEB PHOTO ALBUM. Jack clicks this button, and works his way through the process of setting up an on-line photo album. This includes selecting photos from the shoebox, as well as selecting layout and style. One of the check-box items Jack is offered is “Make this album a camera Action List Item”. Jack doesn't know what that is, so he clicks the Action List link, which brings up a brief description “If you check this box, you will be able to send pictures directly from the camera to this photo album!” Jack finds this interesting, so he closes the description window, and checks the box. Jack also enters the email address for his parents and his wife's parents, so they can be notified to come and see his photo album, which he has entitled “Our First Baby”.

One of the buttons Jack does not click is the “Complete Account Setup” button. He knows that he has 30 days to do that chore, and figures he will get back to it later.

Jack's wife arrives home from shopping at this point, and Jack wants to show her how the new camera works. He starts by showing her the baby album on the PC, then decides to take some pictures of them holding the baby. Jack then selects the images, and presses the “Send” button again.

Since his cell phone is still on, sitting on the table a few feet away, the connection goes smoothly and quickly. A new dialog pops up, surprising Jack. It says “Select the destination for your pictures” and offers two choices: “My Shoebox” and “Our First Baby”. Jack is amazed, he doesn't realize that the server 18 downloaded his action list to his camera during the connection. Jack decides to select the “Our First Baby” web album as the destination for the images, and clicks OK. The pictures are sent as before. After the transmission has completed, Jack goes to the PC to check on the photo album. When Jack refreshes the album page, he now sees the additional pictures he just sent, along with the pictures he sent before.

Jack spots a “Send Prints” link on the web page, and clicks it. He is led through a selection of print types, mailing addresses, and credit card info to make it possible to send prints. He is offered the option of completing the setup of his account. Jack decides to do that now, and proceeds to fill out the requested information, including his credit card number. Once the account setup is complete, Jack continues the print order. One of the radio button items is “Make prints a separate Action List Item” or “Make prints part of your Action List”. Jack remembers something about Action Lists from before, but is not sure what this means. The description says “Making a separate action list for prints allows you to decide in the camera to send to the photo album and send prints or to just send to the photo album.” Jack thinks this is cool, and checks the “Make prints a separate Action List” item. The next time Jack sends photos from the camera, his action list will be updated to present three choices: My Shoebox, Our First Baby, and Our First Baby w/Prints.

The underlying technology supporting this scenario are summarized below. Other functions and features are assumed, but not required for this scenario:

1. Two-way connection between camera and portal 2. Camera metadata included in the request 3. If not using an IP direct connection, 3.1. Default ISP connection info built into the camera for the first connection (country specific) 3.2. Downloaded assigned ISP information from the portal to the camera 4. Software capable of recognizing automatically a set of supported phones and adjusting the protocol to match 5. Action Lists maintained on the server that are automatically downloaded to the camera to update the camera selection list each time a connection is made 6. An On-line shoebox 7. Ability to download files to the camera from the server. The files could be text, GIF, animated GIF, JPG, or even a script or applet. This feature enables the ability to display advertisements on the camera, remind the user of remaining time to complete account setup, make special offers, and indicate limits reached.

A method and system for automatically configuring a web-enabled digital camera to access the Internet has been disclosed. Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. For example, although the photo-sharing service has been described as including the gateway server and the database, the database may be located elsewhere. Also, the gateway server may be used to control account information, while one or more other servers may be used to provide the web pages of the entity-specific websites. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims. 

1. A method, comprising: displaying, on a device, an action list received from a server, the action list comprising actions performable by the server on images stored on the device; receiving, by the device, a selected action from the action list; uploading, by the device to the server, at least one selected image from the images; and transmitting by the device to the server, an instruction for the server to perform the selected action on the uploaded image in response to the receiving the selected action.
 2. The method of claim 1, further comprising transmitting, from the device to the server, identification information for the device, wherein the action list received by the device is associated with the identification information.
 3. The method of claim 1, further comprising transmitting, by the device to the server, an email address, wherein the selected action comprises sending, by the server, the at least one selected image to the email address.
 4. The method of claim 1, further comprising transmitting, by the device to the server, a storage location, wherein the selected action comprises storing, by the server, the at least one selected image in the storage location.
 5. The method of claim 1, wherein the action list is displayed in response to the device receiving an image upload signal.
 6. The method of claim 1, wherein the device comprises a digital camera configured to capture the image.
 7. A device, comprising: a memory device configured to store instructions; and a processing device configured to execute the instructions stored in the memory device to: display an action list downloaded from a server in response to an image upload signal, the action list comprising actions performable by the server; receive a selected action from the action list; upload, to the server, at least one selected image stored on the device; and transmit, to the server, the selected action to cause the server to perform the selected action on the at least one selected image uploaded by the device to the server.
 8. The device of claim 7, wherein the processing device is further configured to execute the instructions stored in the memory device to transmit, to the server, an entity ID to cause the server to retrieve the action list from an account associated with the entity ID.
 9. The device of claim 8, wherein the processing device if further configured to execute the instructions stored in the memory device to: receive at least one action to include in the action list; and transmit, to the server, the at least one action to cause the server to append the at least one action to the action list in the account.
 10. The device of claim 7, wherein the processing device is further configured to execute the instructions stored in the memory device to transmit, to the server, an email address, wherein the selected action comprises sending, by the server, the at least one selected image to the email address.
 11. The device of claim 7, wherein the processing device is further configured to execute the instructions stored in the memory device to transmit, to the server, a storage location, wherein the selected action comprises storing, by the server, the at least one selected image in the storage location.
 12. The device of claim 7, wherein the processing device is further configured to execute the instructions stored in the memory device to: store the action list in the memory device; retrieve the action list from the memory device in response to a further image upload signal; and display the action list retrieved from the memory device in response to the further image upload signal.
 13. A method, comprising: identifying, by a server, an action list for transmission to a device based on an identifier received from the device; transmitting, by the server to the device, the action list comprising actions performable by the server on images stored on the device; receiving, by the server from the device, a selected image selected from the images stored on the device; and performing, by the server, a selected action received from the device on the selected image, the selected action being selected from the action list.
 14. The method of claim 13, further comprising: identifying, by the server, an account associated with the identifier; and selecting, by the server, the action list to be transmitted to the device from the account.
 15. The method of claim 13, wherein the method further comprises sending, by the server, the selected image to an email address received from the device in response to receiving the selected action.
 16. The method of claim 13, wherein the method further comprises storing, by the server, the selected image in the storage location received from the device in response to receiving the selected action.
 17. The method of claim 13, further comprising: accessing, by the server, an account of a photo-sharing website associated with the identifier; identifying, by the server, at least one action associated with the account that was performed by the server; and generating, by the server, the action list based on the at least one action.
 18. The method of claim 13, further comprising generating, by the server, the action list based on a signal received from the device indicating at least one action to be included in the action list.
 19. The method of claim 13, further comprising: identifying, by the server, at least one action performed on an image from a website; displaying, by the server, a prompt on the website inquiring whether to add the at least one action to the action list; and adding, by the server, the at least one action to the action list in response to the server receiving a signal indicating that the at least one action should be added to the action list.
 20. The method of claim 13, further comprising identifying, by the server, an entity associated with the device based on the identifier, wherein the action list comprises a default action list associated with the entity. 